Overview of the Action Object Manager

The Action Object Manager provides a simple and easy way to deploy and monitor Action Objects. Making use of the Microsoft Management Console (MMC), and provided as a snapin to MMC, the Action Object Manager allows you to easily maintain all your Action Objects from one central point of access.

An Action Object (AO) is the name given to an executing configuration, which could have been created and deployed from a number of sources, including Architect, Cause+, Process+ and SPC+ to name a few. An executing Action Object is an OPC Classic Server, and can be connected to from OPC Classic clients.

Action Objects:

There are different types of Action Objects that can be deployed:

Event-based Action Objects
Process+ Action Objects
Real-time Action Objects
Scheduled Action Objects

Clicking on the Action Object root will display the total number of Action Objects of each type that are currently executing, are scheduled to execute or are in an error state.
A list of different types of AOs created in and deployed from different applications is given.
Each AO configuration window will be customized according to the type of AO added.

Event Viewer:

The server logs any events, including error messages in the application log of the Windows event log.
The server will make entries in the log when an Action Object fails to start executing and when the Action Object Manager reports a error during an operation.
Messages are also logged when an Action Object stops executing. This typically happens when a user stops the Action Object server used to deploy the Action Object.

Notes:

During the Action Object Server startup, if a connection cannot be made to the SQL Server, the Action Object service will delay the start of Action Object deployments. The status of deployment will show as "Starting" and an appropriate message will be logged in the Event Viewer application log. Action Objects will not be deployed until connection to the SQL Server can be established.
To keep log space requirements low, the Proficy CSense Runtime Database is set to use SQL Server's Simple recovery model rather than the Full recovery model. Make sure to schedule regular database backups to protect yourself from data loss and to truncate the inactive portion of the transaction log.